File: XP-Threadripper.png (169 KB, 1920x1080)

169 KB PNG

bump

>>78840642
>24 cores
kek

File: WinNTtan.jpg (32 KB, 200x200)

32 KB JPG

Have there been any major discoveries regarding XP's theme engine? I'd be interested to see what can be done with it.

File: xtzr2zi1xxoh8y4xn42wksscq(...).jpg (42 KB, 600x603)

42 KB JPG

>>78840744

bump

bump
this thread is getting slower and slower

>>78841883
In this particular case, people keep shitposting in the old thread and bumping it, thereby taking attention away from this one.

All the low-hanging fruit (actually figuring out how to compile it, copying files from working retail XP so it works, etc.) - the stuff a bright ten year-old can do - has been done, and therefore it's now beyond the ability of /g/ to improve it further.
Frankly, having been here for years, I'm amazed you faggots got this far without reformatting your hard drives by accident.

So, how stable is the current version? Were there any bug fixes or we're still trying to compile. Have been busy for past month and not sure where everything syands. Is there a todo list?

>>78842041
It's probably about as stable as RTM 2k3 is, some even build from the os they're compiling on, though there were some stability issues with old exinit/systime.c We have a good exinit/systime.c replacement now and replaced precompiled winlogon with one patched from the leaked 2000 sources, and since it has no WPA shit, pidgen.dll was modified to accept any product key. And lastly, some anons are currently trying to get some win10 software working, and have 2 kernel32.dll functions left.

>>78842125
Nice, any chance of getting directx 11 on it? Or is closely tied to the kernel

>>78840571 →
>>>78838051 →
>I'm getting these errors when I try to build
forgot to include it
20201123__KERNEL32.DLL.v2.zip fixes that
note that I put the _ prefix before this extra file

https://gofile.io/d/l2OusB

>>78842349
Have you read >>78840134 → yet? I think it'd be useful for what you're doing.

Bump for mercy sake!

>>78842031
yeah there such idots in there I agree with you the best was the one that think that amd64 mean you have to an amd CPU. And yes he was saying "I have one years of course in C++ I can help if you want". To go on with this we need good people that understand bot HW and SW. It's not trivial to write and os

>>78842349
yes thx, I just tried it
I added this basic implementation to _process.c and GetActiveProcessorCount to kernel32.src - Python 3.9 still need something for GetLogicalProcessorInformationEx which should be based off GetLogicalProcessorInformation just returning one processor group then with the bare minimal of info.
```cpp
DWORD GetActiveProcessorCount(
WORD GroupNumber
)
//assume one group of processors :-) - needs to be updated to represent the actual combination maybe... NUMA cores etc
{
SYSTEM_INFO siSysInfo;
GetNativeSystemInfo(&siSysInfo); //switched to GetNativeSystemInfo as it works under Wow64
return siSysInfo.dwNumberOfProcessors;
}
```

File: screencap.jpg (42 KB, 805x316)

42 KB JPG

How do I install JDK8 on WIndows XP?
https://stackoverflow.com/questions/20965564/installing-jdk8-on-windows-xp-advapi32-dll-error
When I extract the .exe file there seems not to be any "tools.zip" file on It.

>>78843367
ADVAPI32.DLL seems to be missing (at least) one function that is available in a slightly different form through KERNEL32.DLL as RegDeleteKeyA, would that be in place there is good chance that the installer would run.

>>78843551
What? Im following the link I sent you and I don't know what you are talking about. Please tell me what should I do to make It work.

>>78843367
see >>78843395 →
it works for installers that can't be normally extracted with 7-zip (like for ex. drivers)

File: fuck netframework.jpg (30 KB, 1160x159)

30 KB JPG

>>78843788
Do I really need to install NetFramework?

>>78844344
.NET framework 4.6 doesn't work on XP/2003.

>>78844373
What to do then?

Did the WinPE Anon make any progress with getting a working PE iso?

>>78844383
Change Windows XP's source code and add support for .NET Framework 4.6

>>78845204
WinPE already working
add opktools to base\ntsetup\dirs bz in ntsetup then
tools\postbuild.cmd and tools\oscdimg.cmd winpe

>>78845339
Oh wow okay, cool!

bump

File: 1606104469974.gif (2.07 MB, 244x180)

2.07 MB GIF

How do I get rid of Activate Windows without paying?

>>78846461
Replacing winlogon with the win2k one and using cracked pidgen.dll with all F product key should do the trick.

>>78846461
Oops I'm a retard
Didn't notice this was xp thread

bump

>>78846472
>cracked pidgen.dll
Totally not a keylogger

>>78846486
It's really just a modded pidgen from the XPSP1 sources I think, so source is available

>>78840611 (OP)
needs a qrd though.

Do the !ifdef in makefiles look for environment variables or something? I need to define something to get a component to work properly and !define just spat out errors/warnings.

>>78846650
I know that ifdef in base\prerelease.inc can be switched by "set PRERELEASE=1"

>>78847516
Thanks.

winxp livecd when

>>78847781
If you mean an installer disk, you already can. Follow the guide.

>>78847893
He means a live cd like booting Loonix off a live cd

So the first beta of SP can be made run on intel CPU by patching the kernel, in KiInitKernel ther eis a check that detect if the cpu vendor is GenuineAMD otherwise it bugcheck. It does so via calling strcmp and it use a jnz op to see if it need to bugcheck. If we patch the kernel and change the opcode to jz than the build only work on intel CPU (I mean also other CPU vendor but afaik found somebody else having silicon for amd64).

>>78847781
>>78847893
>>78847990
Isn't Win PE basically that?

>>78848169
Yup

>>78845243
>backporting kernel API from NT 10
retard

>>78848196
I told him to no wasting his time. But nope, now he is at the point where kernel changes are different. Without considering the most problem of all KASLR is not a thing in XP!

>>78848278
>KASLR
whats KASLR?

>>78848351
kernel address space layout randomization

>>78848351
https://en.wikipedia.org/wiki/Address_space_layout_randomization#KASLR

>>78848360
Basically the way why OS are more secure now, if that is not broken.

>>78848369
Boy it's to difficult in here to search online before asking anything and again why you are doing anything with kernel if you don't know this stuff. This is the problem why software is bad today people do stuff without knowing anything of the hardware and lower stuff.

>>78848278
Why would you need KASLR, that is a security feature is it not, its not actually needed for software to function.

>>78848402
And on such an old OS, does it matter

>>78848402
Because maybe some software used that fact to perform some trick? Here his goal is to have compatibility.....

>>78848196
>using wine

Yet another ReactOS?

Now how can I extract an compress file of an windows install ISO?

It would be better to write something like a kernelex for XP

File: aline-hirata-thisisfine.jpg (524 KB, 1920x960)

524 KB JPG

>>78848402
> Lets hackplement Win10 support like ReactOS does, but with the difference we have windows code, so there isn't excuse for hackplementing stuff in first place...

>>78848559
KernelEx already exists... Is shit. Don't reinvent shit wheels.

>>78845243
What tools are people using to backport this stuff. I see dependency walker is being is used to see what is missing but I have no clue where to go from there.

>>78848588
Do you know of a better option?

Now how can I extract an compress file of an windows install ISO?

>>78848627
Kernelex worked fine when it was being developed it's just that no one was interested in extending 98/2k support anymore.

>>78848588
we don't have code for any new win10 functions though so someone has to write that.

This might be useful - DLL Merger
https://www.win-raid.com/t4035f45-Windows-XP-Bit-and-Server-Bit-on-Modern-Hardware-379.html#msg127793

Building opktools:
I get the error
>base\ntsetup\opktools\factory\pid.c(26): error C1083 Cannot open include file 'licdll.h' no such file


Is that a licensing thing I presume?

>>78849777
I think I heard that you can just delete pid.c, but ignoring the error is fine also and everything seems to work still.

>>78849777
https://pastebin.com/raw/qEPGWXsW this should fix it

>>78849863
Thanks! I thought about commenting those two lines out aswell

>>78848181
Here are instructions I was given to get a PE rom built >>78687696 → . But after trying it said finished but didn't pop out any output.
I'm not sure what I might have done wrong

Probably something dumb as fuck, but what's with
>shell\osshell\accesory\notepad
>shell\osshell\accesory\newpad
Notepad and Newpad?

>>78840611 (OP)
Will srv 2008 do the job?

>>78850214
Strange, I am now trying a postbuild will report any successes

File: Peek 2020-11-23 15-29.gif (67 KB, 349x245)

67 KB GIF

>>78850242
Idk, there's two notepad icons in the folder.

>>78850242
I'm probs wrong, but I think new pad was a broken notepad.. clean/rename your bin folder and fresh build new pad see what it spits out

>>78850291
Ty, I'm fugging with this newpad and notepad.
I'ma noob, but love learning this shit. Could someone like the commands in razzle or is there a way to spit them out?
>>78850308
Man, I feel like a tard. Where's the bin folder? The last thing I did like this was webhosting troubleshooting and learning bash and shit.

Currently working on porting XPSP1's startpage code to Server 2003. Compiling with all of the FEATURE_STARTPAGE enabled makes about 210 errors.

>>78850353
It's binaries.x86fre or for checked builds it's binaries.x86chk

>>78850353
Check the guide for build commands

And I mean binaries.x86fre but if you haven't built yet then it wont exist :)

File: Screenshot 2020-11-23 203746.png (9 KB, 665x60)

9 KB PNG

>>78850214
So idk what happened your end but I had no issues:
>I added opktools to ntsetup\dirs

>clean built ntsetup

>dirty full build

>postbuild (which ran makewinpe automatically)

>type 'oscdimg winpe' for the pe image

>type 'oscdimg opk' for the OEM Preinstallation Kit

>>78850423
Oh, ty I literally saw that and it didn't register.
>>78850467
Ok, cool, for adding opktools in I did this

     winbrand   \
     opktools   \

Should be fine right? Gonna try following your process.

>>78850382
what is startpage?

>>78850554
Not sure if WinBrand is needed as its mainly Tablet PC and Media Center branding for Explorer start menu

>>78850578
https://betawiki.net/wiki/Windows_XP_build_2410_(main)#Start_Page
Sort of like the Windows 8 start menu, but in a beta version of XP. The code for it is in the XPSP1 sources in the leak.

>>78850417
I'm having two convo's now and confusing myself some. OK, so I have the binaries.x86fre from my initial clean build (right?).
>And I mean binaries.x86fre but if you haven't built yet then it wont exist :)
You're meaning dump that whole folder and rebuild? So fucking sorry for my dumbassery.
>>78850620
Oh, no, I mainly was showing that i just added it there and assumed it's right, I've read and gone over a good amount of code but I'm still unsure sometimes if it placed it in the right place.

>>78850685
Don't delete it, just rename it so it's easier to see exactly what was built for new pad

>>78850685
And ahh okay either way ot should be okay building still, I know the feels lol..

>>78850467
The OEM Preinstallation Kit is missing some files upon installing, mainly IA64 and documentation.. will post the missing files soon

>>78850298
>>78850308
it looks like "new pad" was intended to support xml and html-specific formats, but is dated 2000, while notepad in the same tree is dated 2001 and lists a couple bugs they had written workarounds for in June of 2001.

I believe "new pad" might have been from the Neptune project and merged into the source tree when Neptune was cancelled.

The full-screen startpage stuff is also from Neptune.

>>78850926
Why do they keep these redundent folders when they only contain unused code? It can't possibly be for compatibility.

>>78850926
That's actually quite interesting, I wonder if its usable when compiled

>>78850760
Yeah, I did the rename thing, very used to that, but really, I'm fucking around, I don't need it right? lol
>>78850926
Very nifty, they can both be built right? I'm doing a new clean build to try and get PE but after I could just run bz from the newpad folder and it'd compile?

>>78850760
Too many missing files, gunna extract and check the XPSP1 src, anyone want to quickly check sizes between opktools folder?

>>78851112
Nahh you don't need need it, but I am the same I like messing with stuff in there!

And yeah building newpad will compile and place it in binaries.x86fre for you

>>78851143
So I had ran that already, and I did rename the binaries folder, but I don't see where it is. Or am I mixing things up?

>>78851250
Idk someone else may have to jump in here, idk if newpad is set up to be binplace ect

>>78851025
Why? Because they test some concepts and not necessarily use them, but they can get back to them in future Windows release as all NT version has common base code. Start page didn't fit into XP, but it came back with Windows 8.

>>78851287
K. Do you happen to know if I could find where it would output? like something in the stuff compiled, or is that waaay to deep?

>>78851505
That just makes it so bloated. I still don't get it. Why didn't they put the scrapped concepts in separate repos instead of in the same Windows source repo.

>>78852300
>Why didn't they put the scrapped concepts in separate repos instead of in the same Windows source repo.
Obfuscating potential source code leaks just like this one could be the possible purpose, but let's just assume Microsoft's incompetence.

>>78852453
Most likely a mix of the two.

So oscdimg just creates folders from folders in binaries.archbuild

You can make ISOs of the msbuild tools, IDW and a few other things like Server Adminolistration components and other stuff..

>>78852576
oscdimg.cmd was made by someone in these threads, the leak didn't include any official scripts for creating the iso

>>78852704
Ahh okay I see lol

>>78852704
oscdimg.cmd just wraps oscdimg.exe which is already in the sources and is what actually creates the iso

How the checksum of windows system file is calculated and apply during postbuild process? Anyone have some idea?

>>78853385
The pointis that I have patch both ntoskrnl and ntikrnlmp of sp1beta to basically allow me to both the os on an intel CPU by reversing the comparision (code used jnz (0x75) and I replaced with jz (0x74)) . Now if I replace the file on an arelady installed OS it work like a charm . But during setup it fail the integrity check (as the checksum is off course changed).

Basically my fix invert the cose so now the iso will bugcheck on AMD cpu and work on all other vendors

>>78853450
>>78853385
might be related to sfcgen/winfusesfcgen.cmd in postbuild folder

/gitbucket/emptyset/trident
creating repos for every major component and using submodules. god help me.

>>78854132
I wanna still remind every body that MS had to modify github in order to switch. We will have the same problem they did manage such a big codebase

Unsure if relevant or not but as a fan or /vr/ it appears "BlueSky Software" had some hand in Windows stuff, their wiki doesn't mention it and Quick search can't find much.
>srv03rtm\sdktools\apimon\help\rhhc.bat
Lemmie know if I'm a tard or does it look like they helped generate help files?

>>78840611 (OP)
Fucking windows 10 deleted my winloader off my fucking flashdrive and said it was a virus. You have to rename the file before you use it on a Windows 10 machine or it will get deleted.

God damn I fucking hate Windows 10, fucking fisher price bloatware piece of garbage.

>>78840611 (OP)
anybody here have any experience with windows server OS? Are the more recent versions as malignant and cancerous as windows 10 or are they still pretty much the same?

Has anyone mirrored this file? It seems like anonfiles won't allow downloads for it for maintenance apparently, https://anonfiles()com/t5F468dep1/encdecptr_7z

>>78854613
It's deleted tons of shit for me, just make exceptions, though probably not for a whole thumbdrive.

>>78854568
That kinda looks like a generated file, maybe bluesky makes a tool used to create help files

>>78854613
The only reason i upgraded was because of the hardcap on RAM that Windows 7 had and cause my cd copy was getting really buggy / scratched.

The new UEFI shit on motherboards is fucking cancer, I'm not even sure the new chips are faster.

>>78854650
https://en.wikipedia.org/wiki/Adobe_RoboHelp
>and Blue Sky Software released version 1.0 in January 1992.[2]
>Blue Sky Software was founded in 1990 and changed its name to eHelp Corporation on 4 April 2000.

>>78854650
Right, exactly, they seem to only be known for games, seemed cool. Thx for insight

>>78854648
I don't think it matters, its hardcoded or some shit. There are a million fucking things Windows 10 won't let touch or fiddle with.

I had about a dozen peices of bloatware in my add/remove programs folder alone from Microsoft, and about half of them had no option to uninstall.

>>78854668
Go fucking figure, I see, thx
>>78854679
Yeah

>>78854679
everytime i do a new install of a windows OS I always forget something.

I wish there was a way to just copy paste the drivers. So many drivers come with malware 'software packages' now, the only useful ones are the video drivers cause they have a video capture build in. Everything else is autoupdate crap that never includes a rollback feature for when the driver updates inevitably break your computer.

>>78854706
You can use DISM to extract Drivers from your currently installed system before reinstalling

>>78854706
>Drivers
>Browser Links / Favorites
>Pictures / Music / Videos / Documents / Downloads

I have all my open source stuff on an second harddrive, which i will disconnect when I do a new install. I think I also need to download java and find an old copy of adobe acrobat, maybe minecraft, should probably write down all my old passwords in a booklet or something..

am i forgetting anything? When I get back from my vacation I'm going to install a windows server OS, hopefully put all this Win 10 nonsense behind me. I thought about enterprise but its still cancer and I have to pay for it.

I'm not too keen on paying 500 bucks for a server license but i think i can get an old one for like half that, unless anyone knows where I can download a clean iso to burn to disc.

>>78854787
>buying a copy of windows server OS
>for the same price i could buy a gun and shoot Bill Gates in the head.

>>78854835
>buying a copy of windows

>>78854743
Who cares what you do, you're posting in a thread involving leaked legacy source code where the end game ends in a pirated illegal iso..

We just gunna tell you to stop being a fass and just download a cracked version for freeeeee

>>78853450
I hit the end of the road. I can change the check and the file got installed fine but during the graphical part of the installer, when you have to enter product key ecc, sfc got run. sfc use the file has + signature to detect the integrity. Of course my modified file fails such a check so they got replaced back with original file. So basically when that part of the setup is completed the system reboot forever. At that point you have to copy back the kernel file. It sucks. And we cannot sign the file because we need a private certificate but even our original cert for 2003 would not work as it was expiring on august 2003 and this build is September. (But anyway I think MS would use different cert when publish a build). End of the road.

win10 server is almost the same as win10 pro. Nothing will change for you and you will get more boring stuff like you cannot use IE if you don't disable stuff. Also some software don't run on server sku be careful

and what the fuck this thread become??? Why we are speaking on programs, win server, and deleted files? Why in this thread there are people that have not idea on how a pc/windows work?

>>78854933
Whenever i think i find a clean iso download it always turns out to be bugged / fucked. Plus, like I said, I don't have winloader anymore because fucking win 10 nicked it off my flashdrive.

>>78855118
then i'm going to get an older version of Windows Server, one that doesn't have the hardcoded RAM cap and can use DDR 4 RAM

>>78855040
can't you fuck with the clock and tell it its 1999 or something?

>>78855226
or is the cert verified on their end?

>>78855226
you did not understand the problem. I can change the checksum of file but with no private key I can't resign the file. Windows check the signature of a file for security using public key * private key and the hash of the file. It's basic cryptography. Changing dates and so change nothing.

>>78855135
i dunno, figured a windows xp thread would be a good place to discuss outmoded windows software and bypassing win 10 fuckery.

>>78855135
Because is about Windows XP. This topic seems to attract toddlers, scriptkiddies and gaymers a lot. ReactOS had similar problems before they became ruthless at their forums and chat systems, and started to just ban them.

what is changed now is the file hash, yes by only changing a 0x75 to 0x74 in a 6Mb file. The hash of the file used to generate the final final signature.

>>78855321
Nope inbecile, it isn't.

>>78855321
no here we have to discuss on the leak and the source code, you are free to open a new thread to speak to that stuff.

>>78855316
sorry, you mentioned your cert expiring and I thought maybe if you changed the date you could trick the cert into not doing so, but i guess its not verified on the client end.

>>78855348
go fuck yourself, grognard.

>>78855329
I would do the same as what reactOs did if this was not anon to be honest..

>>78855365
You will go first, brainlet.

>>78855355
No I said that the original srv03 cert expired in august 03. This was why we had to change the clock.

>>78855384
did you just take credit for my idea, you little shit?

>>78855384
Back when the leak come out we did that for one weak than we patch a new cert in the system.

>>78854630
Wrong thread.
See >>>/g/fwt

File: efika_boot.png (10 KB, 724x354)

10 KB PNG

Bump

Double bump.

>>78846472
where do i find them ? newbie here

>>78857610
check /wxp/ - Friendly Windows XP/2003 Leak Thread

>>78857665
you mean the winlogon of 2k and modified pidgen ? There's so many threads

>>78857749
yep, those are in that thread, one of the first posts iirc

bump

>>78857799
lol it was right here on the current post

>>78845243
I would focus on vista stuff. Or longhorn.

is there source code for ohci1394.sys anywhere in the leak?

>>78859039
so do it

I haven’t checked how progress has gone since somebody compiled the server variant but
1. Has XP been properly compiled?
2. Does anyone plan to solve shit like the EternalBlue vulnerabilities and etcetera since this stuff doesn’t even have Service Pack 1 iirc?

>>78859176
We can compile Windows XP from server 2003 retail sources

>>78859371
Has it been done?

File: 1603152338664.png (421 KB, 800x600)

421 KB PNG

>>78859631
yep, pro & home both build fine with the server code
pretty much an x86 version of XP x64

>>78859679
Good, but the leak didn’t have the final version of XP (SP3 w/ EternalBlue fix) right? Any serious release would have to be up to standard.

>>78859884
Don't expect a serious release to come from this leak, its partial anyway and it is outdated codebase.. but it has so many other potentials that can be done with the source.. and it's just a cool project being able to build mutherfuckin Windows XP

>>78859884
Idiot and troller the source is xpSP1!!! Just fucking read the thread title idiot

>>78860055
Obviously it’s not going to derive a new windows on its own, but something based on it could turn up. But if you’re going to use this on the internet at all it’s best if someone makes sure the glaring exploit is patched out because it’s fucking old and was literally the only time MS updated an OS beyond its ended service universally.

>>78860115
Me personally have no interest on going on the net with my build ISOs, but yeah some coming here may think otherwise

>>78860135
If anyone wants to use it for other purposes in the future, fixing it seems paramount to me. Maybe I should learn to code and do my part, but for now I’m just an IT Security student.
Here’s some info if you’ve got any interest.
https://www.avast.com/c-eternalblue
https://www.sentinelone.com/blog/eternalblue-nsa-developed-exploit-just-wont-die/

>>78848483
I meant backporting modern kernel API for modern applications to run

>>78860632
Lets just dump the functions into assembly and recompile them using inline assembly in C __asm

Anyone looked through the zip files throughout the source?

There seems to be a few things (Like Windows ME systempages for HelpCTR)

>>78860222
Win10 doesn’t seem to suffer from EB due to it having SMBv1 off by default, given that the code is on hand, shouldn’t disabling the protocol by default also be possible? Or does XP need it for networking for some arcane reason?

>>78861040
That's imbecile as using wine to "backport" win10 crap to an incomplete codebase isn't even SP1 level. Also, x86-64 msvc compilers don't support inline ASM, so your murky hack would only work in x86.

Stop doing stupidities, and/or taking shortcuts. If you gonna do it, implement the functionality properly. You don't have the same excuse as ReactOS devs, as You have the sources to learn how to do it.

If not, then don't do it. NO ONE NEEDS ANOTHER INCOMPLETE REACTOS HACK OUT THERE.

>>78840611 (OP)
Is there any progress being made on x64?

>>78861363
If SMBv1 is so much concern to you, disable it in your shit. There are people who have uses to SMBv1 out there.

>>78861747
SMBv1 is extremely insecure though. Better be patched if it’s used. The vulnerability is a buffer overflow anyway.

>>78862006
What is this constant obsession with security. I used win2k3 SP2 straight from the iso for many years. If it were not for it becoming obsolete and nothing working on it anymore I would have quite happily used if for the rest of my life.

>>78861668
He don't listen, it's just stupid at this point. This is the problem of stupid people touching stuff like this and why leaks such this should only remain in the hands of people that at least know how an OS work.

>>78862066
Is the NWO speakin on their brainlet marionettes "Give on your freedom in exchange for "security". Remember, we do it for your own good!"

>>78862066
I also never had "security" problems with SMBv1... And I had it even in legacy mode for use with DOS/Win98 machines. Ofc, I was using pfsense firewall rules to isolate segment from the net, like any sane person would do.

>>78848758
Eh not publically but it exists.

>>78862145
Nope... Since MS doesn't do GSPs from newer windowses anymore (now you have to access specific parts to audit from their source depot portal, in read only mode, with your CAC in the smartcard reader). Last GSP was Win7 rtm.

>>78861737
no still missing the amd64 missing archive.

File: PSUDTC-2020-11-24-22-30-22.png (207 KB, 1024x768)

207 KB PNG

We can use tools\ploc\run\autoploc.cmd to make three kinds of Pseudo-Localization build: PSU, FE and MIR.

1. First, compile an USA binary in strict accordance with the tutorial: https://rentry.co/build-win2k3

2. Set a new razzle shortcut for: %windir%\system32\cmd.exe /k D:\srv03rtm\tools\razzle.cmd free offline postbld_dir D:\plocpost, Start in: D:\srv03rtm

3. Create a new txt file, write:

CodePage=1250
ReleaseDir=D:\Release
UAFilePath=D:\UA

Rename it to srckit.psu.ini and copy file into \tools\postbuildscripts

4. edit tools\ploc\run\autoploc.cmd, Search for

if /i "%LANG%" == "psu" (

You will find three results, locate the third result, replace all the "use pushd-popd to enter the directory" method in the IF structure with cd .

Search for

start "Whistler1 running" cmd /c %PlocPath%\run\scriptwrap.bat %sem1% %PlocPath%\plocwrap.bat %ploclogfile1% %_NTPOSTBLD% %PlocPath% whistler1.bat %CodePage% %LOGFILE%

change both %CodePage% to 1250

Same to start "Whistler2 running" cmd /c %PlocPath%\run\scriptwrap.bat %sem2% %PlocPath%\plocwrap.bat %ploclogfile2% %_NTPOSTBLD% %PlocPath% whistler2.bat %CodePage% %LOGFILE%

After modify choose save.

5. run new created razzle shortcut, run:

tools\ploc\run\autoploc -nocopy -nosync -l:psu -c:1250

Wait until it finished, binaries will inside D:\plocpost.x86fre.

File: MIR_NEW-2020-11-07-13-15-41.png (627 KB, 1024x768)

627 KB PNG

Tutorial above is about PSU(Pseudo) build, if you want to create FE(Far East) or MIR(Mirror) build, you need to create srckit.fe.ini or srckit.mir.ini, change things related to codepage to: 932 for FE, and 1256 for MIR.

>>78862066
The exploit was in vogue about 3 years ago but was patched on most systems. Just saying that letting it linger just creates a big and well known hole in security.

File: 1599617783317.png (1.05 MB, 1340x754)

1.05 MB PNG

>>78862319
>>78862415
Lord almighty, the indians and the arabs are starting to come in

>>78862415
That screenshot blows my mind

>>78862489
>never heard of leftsider
Though the expiry date in Hijri calendar is a laff.

>>78862534
I downloaded it after seeing the screenshot, never had such a wonderful Windows 7 ui

psuedocode is the answer!

>>78863407
maybe your pseudobrain?

File: VirtualBox_2003_24_11_202(...).png (25 KB, 800x600)

25 KB PNG

Has anyone gotten SP3 programs to work under a compiled ISO? I tried some of the kernel fixes but still haven't gotten anywhere beyond here.

>>78864004
there is no sp3 for server 2003

>>78864127
I'm talking about programs that require SP3 of Windows XP or SP2 of Windows 2003. Has anyone gotten those programs to work with compiled builds?

>>78864172
won't work because windows reports older version that required

>>78864172
Noup...

>>78864004
Someone is working on Windows 10 compatibility using WINE libraries. They almost have precompiled Python 3.9 working

>>78864327
On the subject of adding NT6x support. There are a few things which need to be addressed. Thread local storage needs to be fixed, which requires significant changes to ntdll. CancelSynchronousIo and CancelIoEx, need new system calls to implement.

Bump

>>78840611 (OP)
Total noob here, should I add .exe files to the .gitignore file?

>>78865992
if you about obj folder, just type in gitignore
**/obj/*

>>78861040
that's retarded, it would be limited architectures and inline assembly isn't recommended because of that

just implement it from what it returns and what variables it needs and what it does

Belated Update on OPKtools and WinPE for anyone interested.. both are still missing stuff, some of the opktools folder can be taken from XPSP1.. but factory.exe is still an issue due to pid.c (applying the fix an anon posted yesterday still gave errors (for me several more)

PE still boots off the ISO though despite factory.exe missing

>>78847781
TinyXP '09 had a live CD version.

File: duce.gif (2.22 MB, 297x229)

2.22 MB GIF

>Disk enumeration starts with 0
>Partition enumeration starts with 1
Who's the brainiac behind this?

File: brainlet_trolling.png (26 KB, 900x781)

26 KB PNG

>>78866594
You're expecting too much from people who doesn't even know how to use C/C++ operators to its fullest.

>>78867931
Yeah there idiots in here that pretend to do stuff without even knowing how the OS works. Is basically what happen in the IT industry overall due to fucking open source mentality, any body can contribute even without knowing what is a branch predictor or what is cache line and what is the size of it on modern CPU. This result in programs getting bad by the day.

>>78867179
>Who's the brainiac behind this?
Microsoft?

>>78868390
>Is basically what happen in the IT industry overall due to fucking open source mentality,
Ehhhh... Actually the problem here is that fucked hexray&copypaste attitude, more than anything else... WINE trolling was there as sideproduct, because some people here feels superior to ReactOS devs, but in the end they just copy blindly on WINE code blocks and call it a day.

>>78869196
yeah people complain reactos and do even worse that them. That is an attitute of beign stupid.

Bump.

So I don't know much about computers and I used windows xp when it came out. Does this source code leak explain why Windows XP corrupts Audio files like mp3 and wma when it caught virus. Corrupted meaning it copies then merges 2 mp3 files in a folder to a single audio file that sounds like both audio played at the same time the cuts off before ending.

>>78870156
Try to read again your question and than ask you if you are a stupid man. If you got a virus is the virus that is messing up your files, lol.
And second people like you is exactly what we don't won't to have on this thread because otherwise it will die.

>>78840611 (OP)
Bump.
Should I use 7 proxies before doing this? Second world European country here.
Is it like normal "piracy" or is it worse?

Created a symsrv dir using symstore.exe with all the XP/2003 symbols packs I could find, SP1/2/3, RTM, beta/RC etc all included, x86/ia64/amd64.

~40GB uncompressed, around ~3GB 7z compressed
It'd need to be decompressed for you to actually make use of it, but it seems symbol server folders can be compressed with the same thing i386 folders use (compress.exe?), so maybe can be recompressed after extracting with a script or something (if I compressed it like that first it'd likely make the 7z a lot larger)

Would anyone here be interested in this? Should work fine with WinDbg/KD/IDA/etc.
I'll try and put a list of all the build numbers this includes too.

>>78871792
i'll gladly host this if you want?

t. git anon

File: 2020-11-24 20-45-41.webm (1.01 MB, 720x480)

1.01 MB WEBM

Is this a common bug while using the Windows 2000 winlogon?

>>78871792
Definitely useful to help Ghidra/IDA's decompiler to spit out more clear C code, as well as making debugging more insightful

Archive.org would want this symbol archive I think

>>78871993
There's a lot of shell-related code missing from our winlogon atm, and screensaver stuff too
Dunno if anyone here is ever gonna fix it up though, winlogon-anon hasn't been seen in a while

>>78871792
Builds included (fre/chk, x86/ia64 & amd64 where available)
>2267.1 Beta
>2296.1 Beta1
>2462 Beta2
>2505 RC1

>2600 RTM
>2600.1106 SP1
>2600.2180 SP2
>2600.5512 SP3

>3590 Beta3

>3790 RTM

>3790.1069 SP1-beta
>3790.1247 SP1-beta
>3790.1260 SP1-beta
>3790.1433 SP1-RC

>3790.1830 SP1
>3790.3959 SP2

Not a huge list since they didn't really release symbol packs for betas that often, most of the released beta-chk builds should be covered though.
Sadly it seems symbol packs for SP betas are pretty hard to find, eg. seems there was definitely a pack released for SP2-RC2 as
>WindowsXP.x86.fre.SP2.RC2.symbols.exe
but an hour spent trying to track that down didn't get anywhere. I wouldn't be surprised if it's on archive.org somewhere though.

For anyone into numbers there's 151968 PDB files in there, 56 different ntoskrnl.pdb variations.

cont.

>>78871912
>>78872016
Sure I don't mind it being rehosted, my upload is kinda bad though so I'll probably have to upload it to one place, and hopefully anons with better internet could mirror.

Packing it now but 7z says it'll be 4 hours or so, pretty sure it'll come out to around 2-3GB (35866MB at 6% compression ratio)

>>78872042
Ah rip

File: IMG_9584.jpg (122 KB, 980x1306)

122 KB JPG

>>78840611 (OP)
What is this thread? an optimized XP build?
My old 9300 has a slow as fuck XP install from 2006 on it and im thinking of doing a fresh install

File: file.png (217 KB, 1394x941)

217 KB PNG

Yo can someone mirror these files for me

File: file.png (36 KB, 510x109)

36 KB PNG

>>78872271
Huh, found a neat doc that mentions that url

File: file.png (40 KB, 384x170)

40 KB PNG

>>78872400
Forgot link
http://www.sonic.net/~undoc/comes_v_microsoft/Supp_Rpt_Andrew_Schulman.pdf
Bunch of source code ZIP filenames in here I never saw before
>WindowsXP_RTM.zip
etc

>>78872428
That's a really interesting thing you found! How you found it I do not know lol

>>78872271
>>78872400
>>78872428
i don't think any of us have access to shared source initiative stuff?

>>78872799
Seems like MSDN premium was part of shared source initiative, no need to be a govt or anything like that, just pay the fee, sign agreements & use the smartcard they provided, so there's a chance someone on /g/ probably did/does have access to it.

Looks like you only got to browse code in-browser and during debugging though, source packages like the ones in this leak were probably from the govt-only shared source stuff.

Wouldn't be surprised if part of the agreement is that you wouldn't try dumping all the code from the codepremium site, very unlikely anyone that had access to this MSDN stuff actually has a full source tree of it, probably just bits and pieces.

>>78872861
also these definitely weren't full trees

>>78872271
>codepremium.msdn.microsoft.com
Pretty neat link, apparently they also gave out VS code at /source/Visual%20Studio%202010/SP1/, and private PDBs at /Symbols.
Wonder what other MS products they shared there. Not gonna lie I'd kill for that VS2010 code tho

>>78840611 (OP)
is it a good idea to use it in 2020? It's likely got viruses all over the internet for it

File: file.png (253 KB, 884x967)

253 KB PNG

>>78872271
lol wtf, using the source server apparently would run sd.exe on the source server itself. I hope someone found a way to play around with that.

Back in 2015 days, was very common for MSDN premium users have to deal with the "Microsoft Software Assurance Transfer Application", and its backend "sd.exe". Since SD.exe logs in MS servers the files you have access, and the percentaje downloaded of them, tied to your CAC smartcard, if you failed to download anything due internet crashes, and the file get corrupted, you had to call MSDN premium support so they could unlock the file from MS side. Sources using SD never were actually distributed as package, but as individual files, and the Smartcard would register how many files you had access on.

That's why everyone gave up that via to get anything substantial, and they focused in the packages MS distributed to their partners. Them probably came from these source dirs ms had server side, with the trees stored as CAB files, just like Windows Update does... But not everything made outside MS. So far, only XP/2003 and Win7 are known to have made it, along with some Office version (dunno if was 2007 or 2010). Ofc, no compiler package source have ever made outside MS HQs.

Also, most probably these links are done right now.

>>78873240
Interesting, thx for the info.
Let's hope the Win7 stuff makes it into the wild eventually.

Just a wild idea, what if somebody could get native Windows comparability on Linux with this shit? I don't know much about coding, but it is just a thought.

A few threads back people were looking for a "clean and untouched" copy of WRK (Windows Research Kernel). Someone pasted this eMule link:

ed2k://|file|[Windows.%E5%86%85%E6%A0%B8%E7%A0%94%E7%A9%B6%E5%85%89%E7%9B%98]Windows.Academic.Program.by.zEalXP.iso|440881152|21E32E165BFF53803972A106FE9CC6BA|h=D5T7UQCA2QIGFWS3YKHRWK5XEL4SKYP3|/

I've finally got the whole file, and sharing it here in case anyone wants it:

anonfiles()com/r386e6t2p5/_Windows._Windows.Academic.Program.by.zEalXP.iso_7z

PS: Took a closer look and looks like this ISO has already been posted before, but I've already uploaded it so might as well share it again. Can anyone verify if this ISO really contains WRK and if it's the latest version. I haven't checked yet.

WRK 1.2 is included in the archive torrent, but the uploader said in a previous thread that he couldn't find a clean copy. Although the checksums seem to be correct.

>>78873064
This is for the source code leak, not general usage of XP.
Go to >>>/g/fwt for that.

>>78872255
Code isn't complete. You could try, but it wouldn't be that good. If this keeps going for another year, it may be a good desktop OS by then, but OpenNTGuy got blackbagged and in general, shit has been slowing down.

I have been working to update OpenXP website and create backup of all chats and documentation in a format that they can accessed forever. If anybody is interested I would upload them somewhere. I am also trying/interested in creating a forum for anonymous discussion on development on onion.

>>78875004
Rentry seems good for this sort of thing, I'll link your docs in the next /wxp/ if you post.

>>78875004
Also a major thing I am suggesting is to create a database of Win XP Post SP1 Updates. We can achieve this by comparing dlls and exes binary level using hex and decompilers and then building a diff for all changes. Progress would be tracked by backporting these changes. Just a suggestion.

>>78875018
Okay I would upload them in html format. Please update all threads post Nov 12 in centrazier threads. I would incorporate them.

>>78872123
Found another symbol pack I was looking for, luckily was buried in some ancient MS download server that wayback archived.

So that's XP RC2 / 2526 located, still on the hunt for these though:
>any SP1 beta/RC
>SP2-Beta1 2055 (symbols EXE)
>SP2-Beta1 2082 (symbol CD)
>SP2-RC1 2096 (symbol CD)
>SP2-RC1 2120 (symbol CD)
>SP2-RC2 2149 (symbols EXE)
>SP2-RC2 2162 (symbols CD)
>SP2-RC1 (WindowsXP.x86.fre.SP2.RC1.symbols ?)
>SP2-RC2 (WindowsXP.x86.fre.SP2.RC2.symbols)
>any SP3 beta/RC

Server:
>RC1 3663
>RC1-Interim 3716
>RC2 3718
>SP1-Beta (3790.1218)
>any SP2 beta/RC

They were all released by MS at some point, maybe through windowsbeta or betaplace though, so might not be able to find on web.archive.org...

>>78875077
In case anyone wants them:
http://download.microsoft.com/download/whistler/install/5.1.2526.0/wxp/en-us/windowsxp.ia64.chk.rc2.symbols.exe
http://download.microsoft.com/download/whistler/install/5.1.2526.0/wxp/en-us/windowsxp.ia64.fre.rc2.symbols.exe
http://download.microsoft.com/download/whistler/install/5.1.2526.0/wxp/en-us/windowsxp.x86.fre.rc2.symbols.exe
http://download.microsoft.com/download/whistler/install/5.1.2526.0/wxp/en-us/windowsxp.x86.chk.rc2.symbols.exe

Will there be any more leaks like lets say for Windows 7?

>>78875227
hopefully

>>78874694
The leak was like 2 months ago, right? I don’t think that people would actually just disappear over XP. Chances are they’re just busy.

>>78875077
Located symbols for 3 more builds too, only x86fre though sadly as these symbols were included on the x86fre SP updater ISO, guess they didn't feel the need to include symbols for other build types that the updater didn't install.
>2600.2055 SP2-Beta
>2600.2096 SP2-RC1
>3790.1289 SP1-RC1
Hope the actual symbols CD/EXEs eventually show up for these some time.

If somebody is interested in porting Aero Desktop and Win 7 look in Win XP should have a look at https://github.com/lee-soft. Have VB6 code for Win 7 Taskbar with Window Thumbnail preview.
Start Menu can be made like Win 7 using by backporting Open-Shell (written in C++) https://github.com/Open-Shell.
For Forks interested into a tabbed film explorer have a look at Open Source ExplorerXP. https://github.com/avrionov/explorerxp
I found a very good implementation of Aero Blur and Transparency effect. A tool named FastAero developed in 2008 or 2009 was opensourced later on but Its source code is lost too. It is very low on resources. It can also help someone trying to give native Win Vista/7 look to Windows Server 2003 RTM. File Explorer updates like Drive Status need to be rewritten if you need them.

Bump

>>78876677
and 2 more x86fre symbols from SP ISOs
>3790.1159 SP1-Beta
>3790.2825 SP2-RC

Pretty sure this is all the symbols I'm gonna find out in the wild for now. Gonna pack them up again and find somewhere to post it now.

Also made a quick bat script that can handle LZX-compressing .pdb -> .pd_, so you can pretty easily recompress them all after extracting (afaik windbg/ida/etc should work with compressed ones fine)

Probably gonna take it a good hour or so to go through 150,000+ PDB files though... once this 7z is packed up I'll give it a try myself and compare the size, if it's not too much bigger maybe I'll just upload the recompressed ones instead.

>>78876681
>If somebody is interested in porting Aero Desktop and Win 7 look in Win XP should have a look at https://github.com/lee-soft. Have VB6 code for Win 7 Taskbar with Window Thumbnail preview.
>Start Menu can be made like Win 7 using by backporting Open-Shell (written in C++) https://github.com/Open-Shell.
>For Forks interested into a tabbed film explorer have a look at Open Source ExplorerXP. https://github.com/avrionov/explorerxp
>I found a very good implementation of Aero Blur and Transparency effect. A tool named FastAero developed in 2008 or 2009 was opensourced later on but Its source code is lost too. It is very low on resources. It can also help someone trying to give native Win Vista/7 look to Windows Server 2003 RTM. File Explorer updates like Drive Status need to be rewritten if you need them.
Nice, thanks, having a look

Bump

File: 20201125_120932.jpg (232 KB, 1440x378)

232 KB JPG

Bump for ie5src.tar

Bump for FastAero sources

Post win7src1.cab+ pls

>>78879022
Idiot idiot and idiot. This is XP leak thread why you fucking post about win7 little fucking maroon?

>>78867179
Because extended partitions are "partition 0".
Nobody knows this ('cept oldfags like me) because we don't use extended partitions anymore.

>>78878544
>>78879022
2600src*.cab would be nice to get too, the XPSP1 package we got is messed up with SP1 shit that stops us postbuilding properly, still haven't seen anyone manage to get that working

File: file.png (217 KB, 682x322)

217 KB PNG

>>78880366
Also seems the 2600src pack had a lot more docs inside which aren't in our packages, sucks they started removing them

>>78880366
How someone could have them? These were cabs never made outside MS, and with codepremium you could "print" only individual only with SD.exe executed remotely, giving it could validate you PKA first.

>>78872428
Cool. I wonder how many files and documents are indexed and just waiting to be found. Though this was a lot easier more than 10 years ago with servers being less secured, I remember one dude in betaarchive finding m$ stuff by trying to connect to all IPs nearby their buildings

File: file.png (115 KB, 867x257)

115 KB PNG

>>78872428
Damn, wish we had that supplemental XP source code too, looks like it has VB5/6 code + MSN + maybe SQL server stuff at least, wonder if it ever got out

>>78881152
>Though this was a lot easier more than 10 years ago with servers being less secured
For source it never have been easy. These are accessed with encapsulated protocols encrypted with a smartcard since 2000s. That's why all the source leaks we have are from MS partners, not from them directly.

>>78881135
>These were cabs never made outside MS
Source? I've seen lots of mentions of MS sharing source packages with vendors/partners, the 2600src*.cab filename pretty much matching up with the leaked 3790src*.cab makes it seem even more like something that was shared out.
I really doubt MS would package the src into .cab files just to be internal-only, I mean they have a source depot right there.

>>78875004
>>78875018
>>78875051
git anon here offering hosting to any openxp related projects

also in terms of like, things that having source for would benefit us a lot: complus is just entirely missing from com/ and that's a huge component of nt5. we can probably build without it but that'll break a lot of miscellaneous nice things in the OS.

File: easy-build (1).png (46 KB, 762x592)

46 KB PNG

Would anyone be able to test my script? Specifically the source patcher and if there are any issues

(I still need to add Winlogon fix and update a few buts just waiting for any further updates on prepatched anon with systime and exinit )

https://www.github.com/Empyreal96/easy-build-nt5/tree/main/easy-build.cmd

>>78881970
I am the only one who does not give a shit about missing pieces? As long as kernel32, user32, gdi32, ntdll, the kernel, and a few other core system files are build-able then I am happy.

>>78882094
a lot of applications depend on COM components(explorer reverts back to windows 2k without them), they were microsoft's preferred way of IPC for a long time. and the system doesn't even boot without uniscribe afaik

>>78882094
It already works on modern hardware too (except maybe UEFI)

>>78881227
>I really doubt MS would package the src into .cab files just to be internal-only, I mean they have a source depot right there.
These packs are frozen snapshots of the main tree and subtrees at a given time. They store them in CABs for easy accesibility by SD.exe daemon and management (individual files don't get missing/fragmentede). Snapshot CAB packing is the same trick used in older Windows Update server system, and it have been replaced with WIMs in newer windows updated versions. Ofc, as you say, they have source depot, but live sessions gives you the latest sources only, and archived sessions used CAB backstores, and now it uses WIM backstores.

>>78882175
What I meant was I am quite happy with using compiled binaries for any component that does not need altering.

>>78882357
It will not work as intented, as windows is a great piramid with components depending on components, unless you want only PE reduced functionality boot images.

>>78882327
Ofc you could request some of these packages, proving you were a government or some really big partner. As have been said since day1 here, so far we know only 2003/XP and Win7 rtm made outside of MS in such way, with russian and chinese government having access to them mainly (and most probably this leak came from a slavic government agency in first place).

>>78882492
Also win7? Are we sure of that?

>>78882492
So far no other MS VIP partner have bothered to get their hands in the sources... Windows codebase is so complex they prefer send their people to Redmond campus to work closely with Windows team instead. That's at least the case of Nvidia, Intel and AMD.

>>78882510
Yes, but was only the RTM snapshot. The information is public in archived news sites.

>>78882544
what you mean? It was still the entire source tree? Have you got link to the articles?

>>78882528
That make sense, but I guess company like intel/amd do also some locally work. Maybe they have part of the tree

>>78882624
So far interviewed people says they only have, and need, private headers and libraries for certain components, but they tend to just use WDK every time they can to minimize dependency on MS favors.

Internal shared work between MS and partners at Redmond is just to implement in Windows certain functionalities the partner request, like for example, some new DirectX functionality in AMD/nVidia case, or Kernel Instruction implementations, in Intel/AMD case.

>>78882603
Yes, is still the "full" source tree, in the level of this leak at least (only some code MS doesn't have, or licensing stuff, is excluded).

>>78882761
So the next leak have to be that ahah

>>78882730
Yeah because I read on C++ bug report blog that AMD/intel do the floating point part of the CRT so I guess they have source for that part. I don't think they go there just for this little thing

>>78882825
They have people camping there "permanently" (aka, some veteran engineers go and newcomer engineers come). So small fixes supposedly are at one matrix call of distance.

>>78882919
And at this time with the pandemic and all, they can request Redmond to have remote drones with azure videoconference integrated. No local source really required, or in words of these partners, even desired.

>>78882919
I see still it's amazing that in 20H02 they broke the floating part of the CRT so some software is crashing. This broke a lot of python dreamers.

>>78840611 (OP)
Just downloaded the code, god its so fucking huge. Might be useful to split this thing into a number of pieces, because its a totally unmanageable size.

>>78883215
Don't even go there.. trust me it will cause a massive debate

>>78883215
Someone was looking into splitting it into git submodules a few days ago, dunno if they made much progress

Useful offline reference for WinAPI/Win32
>Microsoft's Old API Help File Reborn

>With each new version of Windows, Microsoft adds to the API but maintains backward compatibility by never subtracting. All of the information in Win32.hlp is still valid today. In fact, if the same topic as one in Win32.hlp is called up in the latest MSDN documentation it is usually word-for-word the same.

http://laurencejackson.com/win32/

File: Enbvzz8VkAIhKPQ.jpg (59 KB, 680x394)

59 KB JPG

Ahhhh you guys have made so much progress.
I've been stuck with my day job for the last month and I haven't had a chance to work on things.
Does anyone have some catch up items?

I love you all.